fix(cram): honor --force for cached test output - #16237
Open
rgrinberg wants to merge 2 commits into
Open
Conversation
rgrinberg
force-pushed
the
push-wprtrkorkkwq
branch
5 times, most recently
from
August 28, 2026 21:43
b641087 to
0897d6e
Compare
Signed-off-by: Rudi Grinberg <me@rgrinberg.com>
Signed-off-by: Rudi Grinberg <me@rgrinberg.com>
rgrinberg
force-pushed
the
push-wprtrkorkkwq
branch
from
August 28, 2026 22:07
0897d6e to
bdb9c33
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Expose captured stdout as a digest-tracked anonymous build target, then use that target for cached cram results instead of materializing
cram.out. The correction action reads the versionedCRAM-RESULTonly when it executes, preserving cheap null builds while allowingdune runtest --forceto rerun cram tests as requested.